This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Regarding saving: yes, there are a bazillion scenarios where you can't or don't want to save a doc before processing. But to be fair, it's not 100% "there is no way to have LS work with your docs." It's just 97%. ;-)
I consider 8.5.2 to be the first version of XPages that I consider actually appropriate for serious legacy app migration (and it might really take an FP on top of that). The fact that XPages work in the Notes client as well in 8.5.2 is an added bonus, if for no other reason than it further encourages IBM to dump all their dev resources into them from here on out. They are the New Way, whether we like it or not.
But I said it a year ago, and I'll say it now - IBM should have had an SSJS<>LS bridge a long, long time ago.
"2. Once the Agent is done running, the SSJS on the XPage has no ready access to the results, as fields on currentDocument reflect the *old* values before the Agent ran. Deleting currentDocument has no effect. "
Ok, that I didn't know. If that's the case, that sucks, big time. Did you open a PMR about that? I need to check that with 8.5.2 and the new API call that lets you run on an in-memory document.
Feedback response number ECBS85SU4P created by ~Dana Elfreekony on 05/25/2010
Trust me, no Kool-Aid here...
Return to top
Trust me, no Kool-Aid here... (~Sanjay Quettum... 25.May.10) 
